Repository navigation
Add a Rust quickstart with verified document examples - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rust visitors currently reach a Python-first getting-started path. Add a Rust quickstart with a minimal PDF program and a runnable, font-aware example that renders the playground invoice, report, and notice with the published
fullbleed = "=2.5.0"crate. Link it from navigation, the docs home, and the playground.The examples include a lockfile; CI compiles them and compares the actual PDFs and every PNG against the existing native/WASI fixture evidence. No core engine, Python dependency, or release metadata changes.
Validation: Rust 1.97 release build and Rust 1.85 compatibility check passed locally. All three designed PDFs and five PNGs matched the playground output byte for byte, with zero missing glyphs. Strict MkDocs build and 46-page internal-link check passed. The guide was visually reviewed at 390px and 1440px, with no page overflow or JavaScript errors.
Linux CI also passed the full docs/playground checks and reproduced the same Rust-example PDFs and PNGs as Windows. Evidence: https://github.com/fullbleed-engine/docs/actions/runs/36929059647